Skip to content

fix(language-core): do not infer object keys as string literals in v-for #5928

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
KazariEX wants to merge 2 commits into
base: master
Choose a base branch
from
Open

fix(language-core): do not infer object keys as string literals in v-for #5928

KazariEX wants to merge 2 commits into from
+20 −6

Conversation

@KazariEX
Copy link
Member

@KazariEX KazariEX commented Jan 7, 2026 •
edited
Loading

fix #5927

Both for ... in and Object.keys() just return string. Current v-for implement in language tools is not consistent with TS behavior. Inferring the type of key as Exclude<keyof T, symbol> instead of string should be the maximum concession we can make.

@serkodev serkodev mentioned this pull request Jan 8, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[v3.2.0]: v-for with enum key in object doensn't work anymore

1 participant

@KazariEX